Skip to main content
Tunbridge Wells Borough Council

Brownfield land

There is a problem

  • 36 entries must have valid URIs

BFR_0118

SiteReference
BFR_0118
SiteNameAddress
71 - 73 Camden Road, Royal Tunbridge Wells, Kent
Deliverable
yes
HazardousSubstances
Hectares
0.04
MinNetDwellings
NetDwellingsRangeFrom
9
NetDwellingsRangeTo
9
OwnershipStatus
not-owned-by-a-public-authority
PermissionDate
2022-11-25
PermissionType
full-planning-permission
PlanningHistory

PlanningHistory must be a real URL

PlanningStatus
permissioned
SiteplanURL
https://tunbridgewells.maps.arcgis.com/apps/webappviewer/index.html?id=2ae20aa8a81646dcb9cc5280f9d6aab5
GeoX
POINT(0.270005 51.13519)
GeoY
POINT(0.270005 51.13519)
Notes
Development Description: Extant planning application 22/02826/FULL: Change of use and conversion of upper floors to create 4no flats, Retention of the restaurant/cafe units to ground and basement levels, erection of a flatted block to the rear for 5no. flats, with associated amenity space; Site Information: In Limits to Built Development, Ashdown Forest buffer zone, Tunbridge Wells Central Access Zone (Residential), Tunbridge Wells Central Parking Zone (commercial), Shop Front policy, Key Employment Area in Submission Local Plan 2021; Non-Housing Development: Commercial use (restaurant/café) at ground floor and basement level; Proposed for PIP: No
OrganisationLabel
OrganisationURI
LastUpdatedDate
2022-12-31
FirstAddedDate
2022-12-31
EndDate

How to fix this issue

Your dataset is missing the PlanningHistory column.

The Brownfield land guidance explains how to fix the issue:

PlanningHistory

Enter links to any web pages that give information on the site’s planning history (include the “http://” or “https://” prefix). Fields in this column can contain more than one link, as long as you separate multiple links with the pipe character (‘|’). You can leave this field blank.

How to improve Tunbridge Wells Borough Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL